Mitigation of active link alternation by multi-link devices

ABSTRACT

Mitigation of active link alternation by multi-link devices (MLDs) may be provided. First, at least first and second links may be established between an Access Point (AP) MLD and an associated MLD client. The first link may be active, while the second link may be inactive. A set of traffic load data associated with the links may be collected before and after transmission of a Basic Service Set (BSS) load report to the MLD client. The report may include a traffic load on the second link prior to transmission, where the second link is less loaded than the first link. Based on the collected traffic load data, an active link alternation from the first to the second link by the MLD client responsive to receiving the report may be detected. One or more methods for BSS load report management may then be applied to mitigate future active link alternation.

TECHNICAL FIELD

The present disclosure relates generally to wireless networking.

BACKGROUND

In computer networking, a wireless Access Point (AP) is a networkinghardware device that allows a Wi-Fi compatible client to connect to awired network and to other clients. The AP usually connects to a router(directly or indirectly via a wired network) as a standalone device, butit can also be an integral component of the router itself. Several APsmay also work in coordination through direct wired or wirelessconnections, or through a central system commonly called a WirelessLocal Area Network (WLAN) controller. An AP is differentiated from ahotspot, which is the physical location where Wi-Fi access to a WLAN isavailable.

An AP connects to a wired network, then provides Radio Frequency (RF)links (e.g., channels) for other radio devices, such as clientsassociated with that AP, to reach that wired network. Most APs supportthe connection of multiple wireless devices to one wired connection. APsare built to support a standard for sending and receiving data usingthese radio frequencies.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate various embodiments of the presentdisclosure. In the drawings:

FIG. 1 is a block diagram of a wireless network;

FIG. 2 is a diagram illustrating active link alternation by a multi-linkdevice (MLD) client of the wireless network of FIG. 1;

FIG. 3 is a flow chart illustrating an example method for detecting andmitigating active link alternation by an MLD client;

FIG. 4 is a flow diagram illustrating exemplary BSS load reportmanagement methods applied for mitigating active link alternation; and

FIG. 5 is a block diagram of a computing device.

DETAILED DESCRIPTION Overview

Mitigation of active link alternation by multi-link devices includesaccepting, by an Access Point (AP) Multi-Link Device (MLD), anassociation with an MLD client, where a first link and a second link areestablished between the AP MLD and the MLD client, the first link is anactive link over which MLD client transmits and receives data to andfrom the AP MLD, and the second link is an inactive link. Then, a firstset of traffic load data associated with the first and second links iscollected, and a BSS load report is transmitted to the MLD client. TheBSS load report may include a traffic load on the second link obtainedfrom the first set of traffic load data, where the second link is lessloaded than the first link. Next, a second set of traffic load dataassociated with the first and second links is collected, and based onthe first and second sets of traffic load data, an active linkalternation from the first link to the second link by the MLD client isdetected responsive to the MLD client receiving the BSS load report.Last, future active link alternation may be mitigated through BSS loadreport management.

Both the foregoing overview and the following example embodiments areexamples and explanatory only and should not be considered to restrictthe disclosure's scope, as described and claimed. Furthermore, featuresand/or variations may be provided in addition to those described. Forexample, embodiments of the disclosure may be directed to variousfeature combinations and sub-combinations described in the exampleembodiments.

Example Embodiments

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While embodiments of the disclosure may be described, modifications,adaptations, and other implementations are possible. For example,substitutions, additions, or modifications may be made to the elementsillustrated in the drawings, and the methods described herein may bemodified by substituting, reordering, or adding stages to the disclosedmethods. Accordingly, the following detailed description does not limitthe disclosure. Instead, the proper scope of the disclosure is definedby the appended claims.

Institute of Electrical and Electronics Engineers (IEEE) 802.11be ispart of the IEEE 802 Local Area Network (LAN) protocols and introducesthe concept of Multi-Link Devices (MLDs). MLDs may include Access Point(AP) MLDs and non-AP MLDs (the non-AP MLDs also referred to herein asMLD clients). In some aspects, an MLD client may be a multi-radio MLDclient that carries and/or operates multiple independent radios. As partof association of the multi-radio MLD client to an AP MLD, a link may beestablished between the AP MLD and each of the multiple independentradios, where the links may be simultaneously active. In other aspects,an MLD client may have a single radio. As part of association of thesingle-radio MLD client to an AP MLD, multiple links (e.g., at least twolinks) may be established between the AP MLD and the single-radio MLDclient, but only one of those links can be active at a time. Or amulti-radio client MLD may choose to remain active on one link at atime, for example, in order to conserve power.

Various mechanisms may be implemented to assist single-radio MLD clientsin selecting a link from the multiple established links upon which tooperate (e.g., to assist in active link selection). Conventionally, anAP may announce medium conditions on a link (e.g., on-link loadmeasurements) to one or more associated clients active on thatparticular link through a Basic Service Set (BSS) load report,hereinafter referred to as an on-link BSS load report. For example, theAP MLD can announce on a 6 GHz link load parameters on the 6 GHz link. Amechanism may further enable the AP MLD to announce on each link themedium conditions on other links (e.g., out-of-link load measurements)through an out-of-link BSS load report broadcast or transmitted to theone or more associated MLD clients on each link. For example, the AP MLDcan announce on a 6 GHz link load parameters on the 2.4 GHz and 5 GHzlinks using the out-of-link BSS load report. Each of the on-link andout-of-link BSS load reports may include information that indicates howbusy channels of the respective links are, such as channel utilizationand Quality of Service Basic Service Set (QBSS) load. Therefore, thisannouncement by the AP MLD to the MLD client of the medium conditions onother links, in addition to the MLD client's knowledge of mediumconditions on its currently active link, assists the MLD client inchoosing which of the multiple links to select as an active link overwhich to communicate with the AP MLD on. For example, the MLD client maychoose the least-loaded link.

While the out-of-link BSS load reports are helpful to provide thisassistance, it may also lead an MLD client to repetitively alternatebetween active links, e.g., alternate from one link to another link bycontinuously following the least-loaded link upon receipt of anout-of-link BSS load report. This type of pattern may also be referredto as zig-zag behavior For example, an MLD client having established atleast a first link and a second link with an AP MLD may initiallytransmit and receive data on the first link (e.g., the first link is theactive link), but upon receipt of an out-of-link BSS load report on thefirst link indicating that the second link has a lesser load, the MLDclient may alternate active links from the first link to the secondlink. Other MLD clients associated with the AP MLD via the same twolinks may similarly move their traffic based on the out-of-link BSS loadreport (e.g., if broadcasted on the first link). As a result, the firstlink may now have a lesser load than the second link such that when thenext out-of-link BSS load report is broadcast, the MLD client, alongwith the other MLD clients associated with the AP MLD, may once againalternate active links from the second link back to the first link.

In another embodiment, independent of receipt of an out-of-link BSSreport, the MLD client may temporarily alternate from the first linkthat is currently the active link (and of which the MLD client has acurrent traffic load knowledge thereof) to the second link in order toretrieve information about traffic load on the second link to make adecision whether to transmit and receive data over the first or secondlink.

Single-radio MLD clients are particularly prone to active linkalternation based on their limitation of only having one link of themultiple established links active at a same time. However, active linkalternation may also present an issue in multi-radio MLD clients.Accordingly, the disclosure provided herein should not be deemed asbeing limited to single-radio MLD clients but should rather be deemed toencompass multi-radio MLD clients as well; the term “MLD client” isintended to encompass single and multi-radio clients having MLDcapabilities.

The present disclosure is directed to the detection and mitigation ofactive link alternation. Once active link alternation by one or moreassociated MLD clients is detected, variations in BSS load reportmanagement may be implemented by the AP MLD to mitigate the active linkalternation. The variations can include one or more of the following BSSload report management methods: (a) temporarily halting broadcast ofout-of-link BSS load reports by the AP MLD; (b) modifying load values ina unicast BSS load report that is transmitted to an MLD client by the APMLD; (c) performing selective unicast BSS load reporting to one or moreMLD clients by the AP MLD; and (d) disassociating an MLD client from theAP MLD. Each of these methods can be performed individually or invarious combinations. Other variations in BSS load report management mayalso be possible.

The present disclosure provides technical solutions for implementationin a wireless network to mitigate active link alternation by MLDclients. Mitigating active link alternation by MLD clients provides moreequally balanced traffic loads over links supported by a BSS of thewireless network, which serves to reduce latency in data transmissionsas well as achieve gains in throughput (e.g., if channel utilizationmeet a predefined threshold as a result of the load balancing).

FIG. 1 provides a block diagram of an exemplary wireless network 100that supports network devices with multi-link capabilities. As shown,wireless network 100 includes an AP MLD 102 and an MLD client 104 thatis associated with the AP MLD 102 to connect to network 100, where APMLD 102, MLD client 104, and any other clients associated with first APMLD 102 may form a BSS. An exemplary AP MLD 102 includes an integratedradio communication system that includes a plurality of radios andantennas, including radios 103(a) and 103(b) and corresponding antennas105(a) and 105(b). Likewise, MLD client 104 may include an integratedradio communication system comprising a radio 106 and an antenna 107.

MLD client 104 may be a non-AP MLD. For example, MLD client 104 maycomprise, but is not limited to, a phone, a smartphone, a digitalcamera, a tablet device, a laptop computer, a personal computer, amobile device, a sensor, an Internet-of-Things (IoTs) device, a cellularbase station, a telephone, a remote control device, a set-top box, adigital video recorder, a cable modem, a network computer, a mainframe,a router, or any other similar microcomputer-based device capable ofaccessing and using a Wi-Fi network.

MLD client 104 may associate with AP MLD 102 using an MLD setupprocedure (e.g., a multi-link setup signaling exchange) defined by astandard or protocol, such as IEEE 802.11be. As part of the setup, MLDclient 104 may establish multiple communication links, such as a firstlink 108 between antenna 107 and antenna 105(a) of AP MLD 102 and asecond link 109 between antenna 107 and antenna 105(b) of AP MLD 102. Inother examples, more than two links may be established. Each of thelinks may include a communication channel, for example, on one of threeRF bands: 2.4 Giga-Hertz (GHz), 5 GHz, or 6 GHz. As one illustrativeexample, a 6 GHz link may include a communication channel on the 6 GHzband. In some examples, a channel width of a communication channel mayinclude multiple 20 MHz subchannels. Additionally or alternatively, thecommunication channel may be a multiple-input multiple-output (MIMO)channel with multiple antennas on each side.

In some examples, MLD client 104 may include multiple radios. Forexample, MLD client 104 may be a multi-radio MLD client havingSimultaneous Transmit Receive (STR) capability (e.g., a multi-radio STR)or a multi-radio MLD client not having STR capability (e.g., amulti-radio non-STR). In other examples and as illustrated in FIG. 1,MLD client 104 may include a single radio (e.g., radio 106). Forexample, MLD client 104 may be an enhanced single radio MLD client or asingle radio MLD client.

MLD capability enables MLD client 104 to transmit on at least twodifferent links established during multi-link set up. However, based ona type of MLD client 104, a number of links on which MLD client 104 maybe active at a same time varies. For example, if MLD client 104 is anenhanced single radio MLD client or single radio MLD client, MLD client104 may only be active on one link at a time and thus, only capable oftransmitting data on one link at a time. Alternatively, if MLD client104 is a multi-radio STR MLD client or a multi-radio non-STR MLD client,MLD client 104 may be active on, and thus transmit on, two differentlinks at the same time. When transmitting on two different linkssimultaneously, in some examples, MLD client 104 can transmit on twolinks within a same RF band (e.g., transmit on two different channelswithin one of 2.4 GHz, 5 GHz, or 6 GHz bands). In other examples, MLDclient 104 can transmit on two links within different RF bands (e.g.,transmit on a channel of 5 GHz band and on a channel of 6 GHz band).

AP MLD 102 may be a networking hardware device that enables otherdevices, such as MLD client 104, to connect to network 100. As anexample, AP MLD 102 can be configured with a multi-radio softwarecontroller for use with Long Term Evolution (LTE), Wireless Fidelity(Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), GlobalSystem for Mobile Communications (GSM), Code Division Multiple Access(CDMA), Wideband Code Division Multiple Access (WCDMA), etc. thatincludes N (e.g., 2, 4, 8, 16, etc.) independent 2×2 transceivers, Nindependent two channel receivers or sniffers, a radio frequency bandfrom about 70 Megahertz (MHz) to about 6 Gigahertz (GHz), and a tunablechannel bandwidth.

In other embodiments of the disclosure, rather than AP MLDs, devices maybe used that may be connected to a cellular network that may communicatedirectly and wirelessly with user devices (e.g., MLD client 104) toprovide access to wireless network 100 (e.g., Internet access). Forexample, these devices may comprise, but are not limited to, eNodeBs(eNBs) or gNodeBs (gNBs). A cellular network may comprise, but is notlimited to, an LTE broadband cellular network, a Fourth Generation (4G)broadband cellular network, or a Fifth Generation (5G) broadbandcellular network, operated by a service provider. Notwithstanding,embodiments of the disclosure may use wireless communication protocolsusing, for example, Wi-Fi technologies, cellular networks, or any othertype of wireless communications.

For illustrative purposes, wireless network 100 includes one AP MLD 102and one MLD client 104 associated with AP MLD 102; however, one or moreadditional MLD clients may be associated with AP MLD 102 in the BSS anda plurality of other AP MLDs and their associated MLD clients may beused in conjunction with wireless network 100 (e.g., forming other BSSin network 100). Additionally, while MLD client 104 is illustrated as asingle radio MLD client, other MLD clients including multi-radio MLDclients may be used in conjunction with wireless network 100.

Components of wireless network 100 (e.g., AP MLD 102 and MLD client 104)may be practiced in hardware and/or in software (including firmware,resident software, micro-code, etc.) or in any other circuits orsystems. The elements of wireless network 100 may be practiced inelectrical circuits comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements,radio elements, or microprocessors. Furthermore, the components ofwireless network 100 may also be practiced using other technologiescapable of performing logical operations such as, for example, AND, OR,and NOT, including but not limited to, mechanical, optical, fluidic, andquantum technologies. As described in greater detail below with respectto FIG. 5, aspects of wireless network 100 may be practiced in acomputing device 500.

FIG. 2 is a diagram 200 illustrating active link alternation by MLDclient 104 of wireless network 100 of FIG. 1. As previously discussed,at least first link 108 and second link 109 may be established betweenAP MLD 102 and MLD client 104. As shown from left to right, at a firstconfiguration 205, first link 108 may initially be the active link overwhich AP MLD 102 and MLD client 104 are communicating for datatransmission (e.g., transmitting and receiving data), while second link109 is initially the inactive link. Additionally, in this example, firstlink 108 may have a heavier traffic load than second link 109 based ondata transmissions between AP MLD 102 and MLD client 104 (andpotentially one or more other clients associated with AP MLD 102 thatare also active on first link 108).

As part of an example mechanism for assisting MLD clients in selecting alink from the multiple established links upon which to operate, AP MLD102 transmits a first out-of-link BSS load report 210 to MLD client 104on first link 108, where first out-of-link BSS load report 210 includesa traffic load of at least second link 109. In some examples, firstout-of-link BSS load report 210 may include a traffic load on all otherlinks via which AP MLD 102 is communicating with clients on in the BSSexcept the current link on which the report is being transmitted (e.g.,except for first link 108). MLD client 104 may also have knowledge of atraffic load on first link 108 based on an on-link BSS report (notillustrated here) transmitted from AP MLD 102 to MLD client 104 on firstlink 108. The traffic load data included in these various types of BSSreports may indicate how busy channels of the respective links are, thedata including channel utilization and QBSS load metrics.

Responsive to receiving first out-of-link BSS load report 210 thatincludes the traffic load on at least second link 109 (and based onfurther knowledge of traffic load on first link 108), MLD client 104determines that second link 109 has lesser traffic load than first link108 (e.g., second link 109 is a least-loaded link). Based on thisdetermination, MLD client 104 may alternate active links from first link108 to second link 109 to follow the least-loaded link. In otherexamples, even if second link 109 is the least-loaded link, MLD client104 may alternate active links only if first link 108 is also above athreshold channel utilization (e.g., may alternate to second link 109 iffirst link 108 is busy 85% or more of the time).

As a result of the alternation, at a second configuration 215, secondlink 109 is now the active link over which AP MLD 102 and MLD client 104are communicating for data transmission (e.g., transmitting andreceiving data), while first link 108 is the inactive link. In someexamples, dependent on the traffic load of MLD client 104, second link109 may now have a greater traffic load than first link 108 due to thetraffic load of MLD client 104 now on second link 109. Additionally oralternatively, the one or more other clients associated with AP MLD 102that are also active on first link 108 may receive the first out-of-linkBSS load report 210 from AP MLD 102 on first link 108 (e.g., because APMLD 102 transmits the first out-of-link BSS load report 210 in broadcastframes). Upon receipt, a portion of the one or more other clients thatare MLD clients may, similarly to MLD client 104, alternate active linksfrom first link 108 to second link 109 (or another least-loaded link).As a result, second link 109 may now have a greater traffic load thanfirst link 108 due to the active link alternations causing traffic loadof the multiple other MLD clients in addition to the MLD client 104 tonow be on second link 109.

AP MLD 102 then transmits a second out-of-link BSS load report 220 onsecond link 109 to MLD client 104 and, if transmitted in a broadcastframe, to other clients associated with AP MLD 102 having the secondlink 109 as their active link as well. In some examples, secondout-of-link BSS load report 220 may be a next immediate load report thatfollows the transmission of first out-of-link BSS load report 210. Inother examples, second out-of-link BSS load report 220 may betransmitted following one or more additional cycles of active linkalternation. As an illustrative example, rather than transmitting secondout-of-link BSS load report 220 once the second configuration 215 hasresulted from a first active link alternation, second out-of-link BSSload report 220 may instead be transmitted after a third configuration225 (discussed below) has resulted from a second active linkalternation. The second out-of-link BSS load report 220 reports thetraffic load on at least first link 108. MLD client 104 may also haveknowledge of traffic load on second link 109 based on an on-link BSSreport (not illustrated here) transmitted from AP MLD 102 to MLD client104 on second link 109.

Responsive to receiving second out-of-link BSS load report 220 (andbased on knowledge of traffic load on second link 109), MLD client 104determines that first link 108 has lesser traffic load than second link109 (e.g., first link 108 is a least-loaded link). Based on thisdetermination, MLD client 104 may again alternate active links fromsecond link 109 to first link 108 to follow the least-loaded link. Inother examples, even if first link 108 is the least-loaded link, MLDclient 104 may alternate active links only if second link 109 is alsoabove a threshold channel utilization.

As a result of the alternation, at a third configuration 225, first link108 is once again the active link over which AP MLD 102 and MLD client104 are communicating for data transmission (e.g., transmitting andreceiving data), while second link 109 is the inactive link. Based onthe traffic load of MLD client 104 and/or based on traffic load of aportion of one or more other MLD clients active on second link 109 thatsimilarly alternate active links from second link 109 to first link 108in response to the broadcasted second out-of-link BSS load report 220,first link 108 may again have the greater traffic load than second link109. Thus, a pattern is established by which MLD client 104 (and/orother MLD clients) repetitively alternate between first and second links108, 109 responsive to out-of-link BSS load reports transmitted from APMLD 102, e.g., causing traffic load to be repetitively transferred to aleast-loaded link. This pattern may also be referred to as zig-zagbehavior.

In another embodiment, independent of receipt of an out-of-link BSSreport, such as out-of-link BSS reports 210, 220 described above, MLDclient 104 may temporarily alternate from a currently active link (ofwhich the MLD client has a current traffic load knowledge thereof) toanother link in order to retrieve information about traffic load on theother link to make a decision as to which link to transmit and receivedata over. As one example, if MLD client 104 is a single radio clientthen the MLD client 104 may alternatively switch from the currentlyactive link (e.g., first link 108) to the other link (e.g., second link109). As another example, if MLD client 104 is a multi-radio clienthaving a first radio on first link 108, MLD client 104 may temporarilyswitch on its second radio on second link 109. In either example, oncetemporarily on second link 109, MLD client 104 may passively receive abeacon on second link 109 that includes the traffic load information onsecond link 109 or may actively solicit an on-link BSS load report to beprovided on second link 109. Having knowledge of traffic load on firstlink 108 and now second link 109, MLD client 104 may then determinewhether to commit to alternating to second link 109 or maintaintransmission and reception of data on first link 108.

FIG. 3 is a flow chart illustrating an example method 300 for detectingand mitigating active link alternation by MLD client 104 as shown inFIG. 2. Method 300 may be implemented using computing device 500 (e.g.,AP MLD 102) as described in more detail below with respect to FIG. 5.Ways to implement the stages of method 300 will be described in detailbelow.

Method 300 starts at stage 305 and continues to stage 310 where AP MLD102 accepts an association with MLD client 104, and first link 108 andsecond link 109 may be established between AP MLD 102 and MLD client104. First link 108 may be an active link over which MLD client 104transmits and receives data to and from AP MLD 102 and second link 109may be an inactive link (e.g., as shown in first configuration 205 inFIG. 2).

Method 300 proceeds to stage 315, where a first set of traffic load dataassociated with the first and second links 108, 109 is collected. Thetraffic load data may include information indicating how busy channelsof the respective links are, the data including channel utilization andQBSS load metrics.

Method 300 then continues to stage 320, where a BSS load report istransmitted to MLD client 104. In one embodiment, the BSS load reportmay be an out-of-link BSS load report (e.g., first out-of-link BSS loadreport 210) transmitted on first link 108 to MLD client 104. Theout-of-link BSS load report may include a traffic load on second link109 that is obtained from the first set of traffic load data collectedat stage 315. In this example, second link 109 may be less loaded thanfirst link 108. In some examples, the out-of-link BSS load report may betransmitted in broadcast frames (e.g., may be multicast) such that oneor more other associated MLD clients active on first link 108 mayreceive the out-of-link BSS load report. Additionally, MLD client 104may receive a traffic load on first link 108 (e.g., the link on whichMLD client 104 is currently active) through an on-link BSS reporttransmitted to MLD client. Thus, based on the on-link and out-of-linkBSS reports, MLD client 104 may be aware that second link 109 is lessloaded than first link 108. In another embodiment, independent ofreceipt of an out-of-link BSS report, MLD client 104 may be aware thatsecond link 109 is less loaded than first link 108 based on MLD client104 temporarily alternating to second link 109 to receive traffic loadinformation on second link 109 (e.g., through passive receipt of abeacon or active solicitation of an on-link BSS load report). In otherwords, in this other embodiment, the BSS load report transmitted to MLDclient 104 at stage 320 may be an on-link BSS load report transmitted onsecond link 109 to MLD client 104.

Method 300 proceeds to stage 325, where a second set of traffic loaddata associated with first and second links 108, 109 may be collected.Method 300 then proceeds to stage 330 where, based on the first andsecond sets of traffic load data collected at stage 315 and 325respectively (e.g., before and after transmission of the out-of-link BSSload report), an active link alternation is detected from first link 108to second link 109 by MLD client 104 responsive to MLD client 104receiving the BSS load report (e.g., first out-of-link BSS load report210). In other words, MLD client 104 is exhibiting zig-zagging behavioras illustrated and described in detail with reference to FIG. 2. In theother embodiment discussed above, an active link alternation may beresponsive to the temporary alternation to and receipt of traffic loadinformation (e.g., via the on-link BSS load report) on second link 109by MLD client 104.

In some examples, the detection of active link alternation may be basedupon a predefined number of MLD clients (e.g., a number of MLD clientsover a threshold number) being identified as alternating between twolinks. Additionally, or alternatively, the detection may be based ondifferences in traffic load over two links as one or more MLD clientsare alternating active links between the two links, where thedifferences may be obtained from the collected sets of traffic loaddata. For example, if two links show a repeating pattern of loadimbalance (e.g., with the difference or load imbalance being evaluatedagainst a predetermined threshold value or percentage), active linkalternation may be occurring to an extent where mitigation thereof isdesirable. For example, if a load imbalance exists where there isinitially a 15% load on first link 108 and 85% load on second link 109at first configuration 205, for example, and this load imbalance ismaintained but with the 85% load on first link 108 and 15% load onsecond link 109 following transmission of an out-of-link BSS load reportat second configuration 215, for example, active link alternation islikely occurring and to an extent where mitigation is desired to achievebalance among the links. Whereas, if a load imbalance exists where thereis initially a 31% load on first link 108 and a 35% load on second link109 at first configuration 205, for example, and this load imbalance ismaintained but with the 35% load on first link 108 and 31% load onsecond link 109 following transmission of an out-of-link BSS load reportat second configuration 215, for example, active link alternation islikely not occurring, or is not occurring to an extent that mitigationis necessary given the more balanced loads between the two links.

In another embodiment, a plurality of additional sets of traffic loaddata associated with first and second links 108, 109 may be collectedand analyzed using machine learning techniques to identify particulartypes of MLD clients that may be more prone to alternate active linksgenerally and/or under particular conditions. For example, based on avendor associated with an MLD client, a model of the MLD client, and/ora software version run by the MLD client, behavior patterns of MLDclients may be detected from the analysis that may be used to build apredictive model or engine. This predictive model or engine may beimplemented to predict and mitigate an active link alternation by an MLDclient before it occurs. For example, identifying characteristics of anMLD client (e.g., vendor, model, software version) may be provided asinput to the predictive model or engine in order to yield a probabilityof active link alternation occurring and/or particular conditions underwhich the active link alternation may occur as output. The output maythen be compared to a mitigation threshold, for example, to determinewhether or not one or more mitigation methods, described below, shouldbe proactively applied.

Upon detection of active link alternation, method 300 continues to stage335 where AP MLD 102 acts to reduce (or eliminate), e.g., mitigate,future active link alternation through BSS load report management. Insome examples, the mitigation may also serve to reduce or eliminateeffects of the active link alternation detected at stage 330. One ormore mitigation methods may be applied, alone or in combination, andsimultaneously or sequentially. Exemplary mitigation methods aredescribed briefly in turn below, and in more detail with respect to FIG.4.

A first mitigation method may include halting the broadcast ofout-of-link BSS load reports. This first method prevents MLD client 104from receiving information about load conditions on other links, such asan established link that is currently an inactive link. The absence ofknowledge of load conditions on other links by MLD client 104 mayprevent, or at least make it less likely that, MLD client 104 willcontinue to alternate active links to follow the least-loaded linkbecause the MLD client will be unaware that the current link it isactive on is or is not the least-loaded link. In other examples, ratherthan halt the broadcast, incorrect information about traffic load on theother links may be transmitted via the out-of-link BSS load reports todissuade MLD client 104 from continuing to alternate active links.

A second mitigation method may include modifying traffic load valuesthat are transmitted to MLD client 104 in a unicast BSS load report(e.g., a load modification scheme). In some examples, and as describedin more detail with respect to FIG. 4, this modification may beperformed if active link alternation by only one MLD client (e.g., MLDclient 104) is detected. The modification may include adding adetermined traffic load of MLD client 104 to the traffic load on otherlink(s) (e.g., inactive links such as first link 108) that are obtainedfrom the second set of traffic load data. The modified traffic load maybe provided in a unicast out-of-link BSS report on second link 109 tothe MLD client to simulate what the traffic load on first link 108 wouldbe if the MLD client opted to switch its active link back to first link108. Resultantly, MLD client 104 will not, or is at least less likelyto, switch its active link because first link 108 will erroneouslyappear more loaded than it is (e.g., more loaded than second link 109upon which MLD client 104 is currently active).

Additionally, or alternatively, as part of the modification, a trafficload on the currently active link (e.g., second link 109) may beobtained from the second set of traffic data and modified to remove thedetermined traffic load of MLD client 104 to simulate what the trafficload of second link 109 would be if MLD client 104 switched activelinks. This modified traffic load data on second link 109 may beincluded within an on-link BSS report transmitted on second link 109 toMLD client 104. Resultantly, MLD client 104 will not, or is at leastless likely to, switch its active link as its currently active, secondlink 109 will erroneously appear less loaded than it is (e.g., lessloaded than the others link(s) such as inactive first link 108).

A third mitigation method may be a load balancing scheme, whereselective unicast BSS load reporting is performed. In some examples, andas described in more detail with respect to FIG. 4, this thirdmitigation method may be applied when active link alternation by morethan one MLD client is detected. For example, out-of-link BSS loadreports may be transmitted unicast to selected MLD clients on the linkwith the greatest load (e.g., now second link 109) on a one-by-onebasis. The unicast out-of-link BSS load report informs a selected MLDclient of traffic load on a lesser loaded link (e.g., first link 108) toprompt the selected MLD client to switch its active link to the lesserloaded link (e.g., effectively reverse the active link alternationdetected at operation 330). This process may be repeated on a one-by-onebasis for one or more additional selected MLD clients on the link withthe greatest load until a desired or predetermined load balance amongthe links is established.

A fourth mitigation method may include a brute force method ofdisassociating MLD client 104 from AP MLD 102. MLD client 104 may thenbe invited to reassociate with AP MLD 102.

Following the application of one or more of these methods to mitigatefuture active link alternation, method 300 ends at stage 340.

FIG. 4 is a flow diagram 400 illustrating exemplary BSS load reportmanagement methods applied for mitigating active link alternation.Method 400 may be implemented using computing device 500 (e.g., AP MLD102) as described in more detail below with respect to FIG. 5. Ways toimplement the stages of method 400 will be described in detail below.

Exemplary method 400 includes a combination of the first, second, andthird mitigation methods described with respect to FIG. 1. However, thisparticular combination and/or sequence in which the first, second, andthird mitigation methods are implemented is exemplary and not intendedto be limiting. Other combinations of one or more mitigation methods indifferent sequences may be implemented.

As shown, method 400 starts at stage 405 and continues to stage 410where AP MLD 102 may collect traffic load data associated with at leastfirst and second links 108, 109 before and after transmitting anout-of-link BSS load report (e.g. multicast) to one or more associatedMLD clients, including MLD client 104. Each associated MLD client mayhave at least two links established with AP MLD 102. At least a portionof those MLD clients may be single radio MLD clients that are capable ofbeing active on only one of the two links at a time.

At stage 415, based on the collected traffic load data, a determinationof whether active link alternation by at least one of the associated MLDclients is detected. Details regarding detection of active linkalternation are described above with respect to stage 330 of method 300.If no active link alternation is detected, method 400 returns to stage410 and AP MLD 102 continues to collect traffic load data subsequent totransmitting out-of-link BSS load reports. If active link alternation isdetected, method 400 continues to stage 420 where the transmission ofout-of-link BSS load reports in a broadcasted manner may be halted(e.g., temporarily suspended), e.g., the first mitigation methoddescribed herein may be applied.

Method 400 includes optional stage 425, where AP MLD 102 may receive aunicast load request from one or more of the MLD clients to provide theMLD clients with traffic load information on other links (e.g., links onwhich the MLD clients are not currently active on). A solicited responseto the unicast load, if one is provided at all, may be dependent onwhich mitigation method is applied, as detailed below. Method 400 maycontinue to stage 430, where it is determined whether active linkalternation by more than one MLD client has been detected.

If not (e.g., if only one MLD client is detected), method 400 proceedsto stage 435 to determine the one MLD client's traffic load. Thedetermined traffic load of the one MLD client from stage 435 is thenused at stage 440 to modify a traffic load that is included within aunicast BSS load report transmitted to the one MLD client e.g., thesecond mitigation described herein may be applied.

In some examples, the unicast BSS load report may be an out-of-linkreport transmitted to the one MLD client on its currently active link.The determined traffic load of the one MLD client from stage 435 may beadded to a traffic load on an inactive link of the one MLD client forinclusion in the out-of-link report to simulate the load that would beexperienced by the inactive link should the one MLD client alternateactive links again (e.g., switch from its currently active link to theinactive link). This modification may cause the inactive link to appearto have a greater load than it actually does (e.g., greater than a loadof the currently active link), making it less likely for the one MLDclient to alternate active links again.

In other examples, the unicast BSS load report may be an on-link reporttransmitted to the one MLD client on its currently active link. Thedetermined traffic load of the one MLD client from stage 435 may beremoved (e.g., subtracted) from the traffic load on the currently activelink for inclusion in the on-link report to simulate the load that wouldbe experienced by the currently active link should the one MLD clientalternate active links again (e.g., switch from the currently activelink to an inactive link). This modification may cause the currentlyactive link appear to have a lesser load than it actually does (e.g.,lesser than a load of an inactive link), making it less likely for theone MLD client to alternate active links again.

In further examples, both on-link and out-of-link BSS reports having thetraffic load modified as described in the above two examples may betransmitted unicast to the one MLD client on the currently active link.

One or more of the unicast BSS load reports may be sent responsive tothe unicast load request made by the one MLD client, if such a requestwas made at optional stage 425. Otherwise, the reports may be sentunsolicited to the one MLD client. Method 400 then returns to stage 410where AP MLD 102 continues to collect traffic load data subsequent totransmitting out-of-link BSS load reports.

If active link alternation by more than one MLD client is detected atstage 430, the third mitigation method (e.g., the load balancing scheme)described herein may be applied. For example, if alternation is detectedby a group of MLD clients comprising two or more clients that as aresult of the alternation are now active on a more highly loaded link,method 400 proceeds to stage 445, where one of the MLD clients isselected from the group that is active on the highly loaded link.

In some examples, the MLD client may be selected based on priority,where priority may be determined based on one or more factors. Oneexample factor includes a traffic load of the MLD client, where an MLDclient with a greater traffic load may be selected to make a moresignificant impact on load balance efforts (e.g., as discussed withrespect to stages 450 and 455). Another example factor includes a typeof the MLD client's traffic, such as a traffic access category (e.g.,voice, video, best effort, and background) and a susceptibility of thetraffic to disruption. As one example, if an MLD client is running highpriority voice applications that are susceptible to disruption, this MLDclient may be less likely to be selected to avoid such disruption. Asanother example, it may be optimal to invite traffic of a first accesscategory (e.g., voice) to be communicated over one link, while trafficof a second access category (e.g., background) to be communicated overanother link. Thus, if an MLD client has voice traffic that is optimalto be communicated over a link on which the MLD client is currentinactive, the MLD client may be prioritized for selection. As a furtherexample, prioritization may be based on MLD clients' channel qualitieson each link. In other examples, the first MLD client may be selectedfrom the group randomly.

Once one of the MLD clients is selected from the group, method 400continues to stage 450, where a unicast BSS load report is transmittedto the selected MLD client on the active, more highly loaded link. Theunicast BSS load report may include traffic load of other less loadedlinks, such as the current inactive link of the selected MLD client, toprompt the selected MLD client to alternate active links to the lesserloaded link. The unicast BSS load report may be sent responsive to theunicast load request made by the selected MLD client, if such a requestwas made at optional stage 425. Otherwise, the unicast BSS load reportmay be sent unsolicited to the selected MLD client.

Method 400 continues to stage 455, where a determination is made as towhether a predetermined load balance among the links has been achievedafter the selected MLD has responded to the unicast BSS load report(e.g., by alternating active links to the lesser loaded link).

If the predetermined load balance has not been achieved, method 400returns to stage 445 where a next MLD client in the group may beselected (e.g., based on priority or randomly as described above). Aunicast BSS load report may be transmitted to the next MLD client atstage 450, and a determination may be made as to whether thepredetermined load balance among the links has been achieved after thenext MLD has responded to the unicast BSS load report at stage 455.Stages 445, 450 and 455 of method 400 may be iteratively repeated untilthe predetermined load balance is achieved.

If (or once) the predetermined load balance is determined to have beenachieved at stage 455, method 400 proceeds to stage 460, wheretransmission of out-of-link BSS load reports may be resumed in abroadcasted manner. Method 400 may then return to stage 410, where APMLD 102 continues to collect traffic load data subsequent totransmitting out-of-link BSS load reports.

In view of the present disclosure, it can be appreciated that methods300 and 400 provide technical solutions for detecting active linkalternation by one or more MLD clients and mitigating future active linkalternations (and in some examples, also mitigating effects of thecurrently detected active link alternation). These solutions enablebalanced traffic loads among links in a BSS, which serves to reducelatency of data transmissions as well as achieve gains in throughput(e.g., if channel utilization meet a predefined threshold as a result ofthe load balancing).

FIG. 5 shows computing device 500. As shown in FIG. 5, computing device500 may include a processing unit 510 and a memory unit 515. Memory unit515 may include a software module 520, and software database 525, andadditional logic. While executing on processing unit 510, softwaremodule 520 may perform, for example, processes for detecting andmitigating active link alternation as described herein. Computing device500, for example, may provide an operating environment for AP MLD 102,MLD client 104, etc. Other operational environments may be utilized, andthe present disclosure is not limited to computing device 500.

Computing device 500 may be implemented using a Wi-Fi access point, acellular base station, a tablet device, a mobile device, a smart phone,a telephone, a remote control device, a set-top box, a digital videorecorder, a cable modem, a personal computer, a network computer, amainframe, a router, a switch, a server cluster, a smart TV-like device,a network storage device, a network relay devices, or other similarmicrocomputer-based device. Computing device 500 may comprise anycomputer operating environment, such as hand-held devices,multiprocessor systems, microprocessor-based or programmable senderelectronic devices, minicomputers, mainframe computers, and the like.Computing device 500 may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices. Theaforementioned systems and devices are examples and computing device 500may comprise other systems or devices.

Embodiments of the disclosure, for example, may be implemented as acomputer process (method), a computing system, or as an article ofmanufacture, such as a computer program product or computer readablemedia. The computer program product may be a computer storage mediareadable by a computer system and encoding a computer program ofinstructions for executing a computer process. The computer programproduct may also be a propagated signal on a carrier readable by acomputing system and encoding a computer program of instructions forexecuting a computer process. Accordingly, the present disclosure may beembodied in hardware and/or in software (including firmware, residentsoftware, micro-code, etc.). In other words, embodiments of the presentdisclosure may take the form of a computer program product on acomputer-usable or computer-readable storage medium havingcomputer-usable or computer-readable program code embodied in the mediumfor use by or in connection with an instruction execution system. Acomputer-usable or computer-readable medium may be any medium that cancontain, store, communicate, propagate, or transport the program for useby or in connection with the instruction execution system, apparatus, ordevice.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific computer-readable medium examples (anon-exhaustive list), the computer-readable medium may include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, and a portable compact disc read-only memory(CD-ROM). Note that the computer-usable or computer-readable mediumcould even be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

While certain embodiments of the disclosure have been described, otherembodiments may exist. Furthermore, although embodiments of the presentdisclosure have been described as being associated with data stored inmemory and other storage mediums, data can also be stored on or readfrom other types of computer-readable media, such as secondary storagedevices, like hard disks, floppy disks, or a CD-ROM, a carrier wave fromthe Internet, or other forms of RAM or ROM. Further, the disclosedmethods' stages may be modified in any manner, including by reorderingstages and/or inserting or deleting stages, without departing from thedisclosure.

Furthermore, embodiments of the disclosure may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. Embodiments of the disclosure may also be practicedusing other technologies capable of performing logical operations suchas, for example, AND, OR, and NOT, including but not limited to,mechanical, optical, fluidic, and quantum technologies. In addition,embodiments of the disclosure may be practiced within a general purposecomputer or in any other circuits or systems.

Embodiments of the disclosure may be practiced via a system-on-a-chip(SOC) where elements may be integrated onto a single integrated circuit.Such an SOC device may include one or more processing units, graphicsunits, communications units, system virtualization units and variousapplication functionality all of which may be integrated (or “burned”)onto the chip substrate as a single integrated circuit. When operatingvia an SOC, the functionality described herein with respect toembodiments of the disclosure, may be performed via application-specificlogic integrated with other components of computing device 500 on thesingle integrated circuit (chip).

Embodiments of the present disclosure, for example, are described abovewith reference to block diagrams and/or operational illustrations ofmethods, systems, and computer program products according to embodimentsof the disclosure. The functions/acts noted in the blocks may occur outof the order as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

While the specification includes examples, the disclosure's scope isindicated by the following claims. Furthermore, while the specificationhas been described in language specific to structural features and/ormethodological acts, the claims are not limited to the features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example for embodiments of the disclosure.

What is claimed is:
 1. A method comprising: accepting, by an AccessPoint (AP) Multi-Link Device (MLD), an association with an MLD client,wherein at least a first link and a second link are established betweenthe AP MLD and the MLD client, the first link is an active link overwhich the MLD client transmits and receives data to and from the AP MLD,and the second link is an inactive link; collecting a first set oftraffic load data associated with the first and second links;transmitting a Basic Service Set (BSS) load report to the MLD client,the BSS load report including a traffic load on the second link obtainedfrom the first set of traffic load data, the second link being lessloaded than the first link; collecting a second set of traffic load dataassociated with the first and second links; based on the first andsecond set of traffic load data, detecting an active link alternationfrom the first link to the second link by the MLD client responsive tothe MLD client receiving the BSS load report; and mitigating futureactive link alternation through BSS load report management.
 2. Themethod of claim 1, further comprising: based on the first and second setof traffic load data, detecting a difference in traffic load on thefirst link and the second link that meets a predetermined threshold; andmitigating future active link alternation through BSS load reportmanagement when the detected difference meets the predeterminedthreshold.
 3. The method of claim 1, wherein transmitting the BSS loadreport to the MLD client comprises: transmitting an out-of-link BSS loadreport on the first link to the MLD client that includes the trafficload on the second link obtained from the first set of traffic loaddata.
 4. The method of claim 3, wherein the out-of-link BSS load reportis transmitted in a broadcast frame, and mitigating future active linkalternation through BSS load report management comprises: haltingtransmission of additional out-of-link BSS load reports in broadcastframes.
 5. The method of claim 1, wherein the MLD client temporarilyalternates the active link from the first link to the second link, andtransmitting the BSS load report to the MLD client comprises:transmitting an on-link BSS load report on the second link to the MLDclient that includes the traffic load on the second link obtained fromthe first set of traffic load data.
 6. The method of claim 1, whereinmitigating future active link alternation through BSS load reportmanagement comprises: determining a traffic load of the MLD client;obtaining a traffic load on the first link from the second set oftraffic load data; modifying the traffic load on the first link toinclude the determined traffic load of the MLD client; and transmittinga unicast out-of-link BSS load report to the MLD client on the secondlink, the unicast out-of-link BSS load report including the modifiedtraffic load on the first link.
 7. The method of claim 1, whereinmitigating future active link alternation by the MLD client through BSSload report management comprises: determining a traffic load of the MLDclient; obtaining a traffic load on the second link from the second setof traffic load data; modifying the traffic load on the second link toremove the determined traffic load of the MLD client; and transmitting aunicast on-link BSS load report to the MLD client on the second link,the unicast on-link BSS load report including the modified traffic loadon the second link.
 8. The method of claim 1, further comprising: basedon the first and second set of traffic load data, detecting active linkalternations from the first link to the second link by a group of MLDclients, wherein the group of MLD clients include the MLD client and oneor more other associated MLD clients having established at least thefirst link and the second link with the AP MLD, the active linkalternations causing the first link to be a less loaded link than thesecond link.
 9. The method of claim 8, wherein mitigating future activelink alternation through BSS load report management comprises:selecting, from the group of MLD clients, a first MLD client; andsending a unicast out-of-link BSS load report to the first MLD client onthe second link, the unicast out-of-link BSS load report including atraffic load on the first link obtained from the second set of trafficload data to prompt the first MLD client to reverse the active linkalternation.
 10. The method of claim 9, wherein the first MLD client isselected based on a priority of the first MLD client, and the priorityis based on at least one of a link channel quality of the first MLDclient, a traffic load of the first MLD client, and a type of trafficassociated with the first MLD client.
 11. The method of claim 9, furthercomprising: after sending the unicast out-of-link BSS load report to thefirst MLD client, determining whether a predefined traffic load balancehas been reached between the first link and the second link; and untilthe predefined traffic load balance is reached, iteratively: selecting,from the group of MLD clients, a next MLD client; and sending a unicastout-of-link BSS load report to the next MLD client on the second link,the unicast out-of-link BSS load report including a traffic load on thefirst link to prompt the next MLD client to reverse the active linkalternation.
 12. The method of claim 1, wherein mitigating future activelink alternation through BSS load report management comprises:disassociating the MLD client from the AP MLD; and inviting the MLDclient to re-associate with the AP MLD.
 13. The method of claim 1,further comprising: in addition to the first and second set of trafficload data, continuously collecting a plurality of additional sets oftraffic load data; based on the plurality of additional sets of trafficload data, identifying types of MLD clients prone to active linkalternation; and for the identified types of MLD clients, proactivelymitigating active link alternation prior to detecting active linkalternation.
 14. An apparatus comprising: a memory storage; and aprocessing unit coupled to the memory storage, wherein the processingunit is operative to: accept, by an Access Point (AP) Multi-Link Device(MLD), an association with one or more MLD clients, wherein a first linkand a second link are established between the AP MLD and each of the oneor more MLD clients, the first link is an active link over which each ofone or more MLD clients transmits and receives data to and from the APMLD, and the second link is an inactive link; collect a first set oftraffic load data associated with the first and second links; transmit aBasic Service Set (BSS) load report to the one or more MLD clients, theBSS load report including a traffic load on the second link obtainedfrom the first set of traffic load data, the second link being lessloaded than the first link; collect a second set of traffic load dataassociated with the first and second links; based on the first andsecond set of traffic load data, detect an active link alternation fromthe first link to the second link by at least one MLD client of the oneor more MLD clients responsive to the one or more MLD clients receivingthe BSS load report; and apply at least one of a plurality of methodsfor BSS load report management to mitigate future active linkalternation.
 15. The apparatus of claim 14, wherein the BSS load reportis an out-of-link BSS load report transmitted to the one or more of theMLD clients in a broadcast frame on the first link, and to apply a firstmethod of the plurality of methods, the processing unit is furtheroperative to: halt transmission of additional out-of-link BSS loadreports in broadcast frames.
 16. The apparatus of claim 14, wherein toapply a second method of the plurality of methods, the processing unitis further operative to: determine a traffic load of the at least oneMLD client; obtain a traffic load on the first link from the second setof traffic load data; modify the traffic load on the first link toinclude the determined traffic load of the at least one MLD client; andsend a unicast out-of-link BSS load report to the at least one MLDclient on the second link, the unicast out-of-link BSS load reportincluding the modified traffic load on the first link.
 17. The apparatusof claim 14, wherein, based on the first and second set of traffic loaddata, active link alternations from the first link to the second link bya group comprised of at least two or more MLD clients are detected, andto apply a third method of the plurality of methods, the processing unitis further operative to: until a predefined traffic load balance isreached between the first link and the second link, iteratively: select,from the group, an MLD client; and send a unicast out-of-link BSS loadreport to the selected MLD client on the second link, the unicastout-of-link BSS load report including a traffic load on the first linkobtained from the second set of traffic load data to prompt the selectedMLD client to reverse the active link alternation.
 18. The apparatus ofclaim 14, wherein to apply a fourth method of the plurality of methods,the processing unit is further operative to: disassociate the at leastone MLD client from the AP MLD; and invite the at least one MLD clientto re-associate with the AP MLD.
 19. A non-transitory computer-readablemedium that stores a set of instructions, which when executed by aprocessing unit, perform a method comprising: accepting, by an AccessPoint (AP) Multi-Link Device (MLD), an association with an MLD client,wherein a first link and a second link are established between the APMLD and the MLD client, the first link is an active link over which theMLD client transmits and receives data to and from the AP MLD, and thesecond link is an inactive link; collecting a first set of traffic loaddata associated with the first and second links; transmitting a BasicService Set (BSS) load report on the first link to the MLD client, theBSS load report including a traffic load on the second link obtainedfrom the first set of traffic load data, the second link being lessloaded than the first link; collecting a second set of traffic load dataassociated with the first and second links; based on the first andsecond set of traffic load data, detecting an active link alternationfrom the first link to the second link by the MLD client responsive tothe MLD client receiving the BSS load report; and applying at least oneof a plurality of methods for BSS load report management to mitigatefuture active link alternation.
 20. The non-transitory computer-readablemedium of claim 19, wherein the plurality of methods include at least: afirst method to halt transmission of out-of-link BSS load reports inbroadcast frames on the first link; a second method to modify a trafficload on the first link obtained from the second set of traffic load datawith a determined traffic load of the MLD client within a unicastout-of-link BSS load report transmitted to the MLD client on the secondlink; a third method to achieve load balance between the first andsecond links when active link alternation by more than one MLD client isdetected; and a fourth method to disassociate the MLD client from the APMLD.